-------------------------------------------------------
Microsoft Dynamics Retail Management System (RMS) 2.0
Headquarters Readme File
November 2006
 2006 Microsoft Corporation. All rights reserved.
-------------------------------------------------------

This file provides information that supplements the product documentation.


How to Use This Document
------------------------

   To view the Readme file on-screen in Windows Notepad
      1. Maximize the Notepad window.
      2. On the Format menu, click Word Wrap (unless it is already checked).

   To print the Readme file
      On the File menu, click Print.


----------
CONTENTS
----------

1.	INSTALLATION NOTES
	1.1	Upgrading from Retail Management System 1.2 and 1.3
	1.2	Upgrading to Windows Vista
	1.3	SQL Server Service Pack Updates
	1.4	Installation Model
	1.5	Installing Headquarters Client
	
2.	SETUP NOTES
	2.1 	Defining Network Protocols
	2.2	Defining Database Server Information

3.	TROUBLESHOOTING
	3.1	Modifying an Installation 
	3.2	Connecting to the Database Server
	3.3	Creating Databases after Upgrading to SQL Server 2005
	3.4	Microsoft Product Support Services



---------------------------------------------------------------

1.	INSTALLATION NOTES

For installation instructions, see the Headquarters Getting Started Guide. A printed copy of the guide is included in your Headquarters package, and an electronic copy is available in .pdf format in the \HQ folder on your CD.

IMPORTANT!
If you are running a previous version of Microsoft Retail Management System, you should back up your store database before upgrading to Microsoft Dynamics Retail Management System (RMS).


1.1	Upgrading from Retail Management System 1.2 and 1.3

All computers in the enterprise, including store registers, must be running the same release of Microsoft Dynamics RMS.

Microsoft strongly recommends making a backup of your database prior to upgrading.

The upgrade process uninstalls the existing application and all its files before installing the 2.0 release. This means that any files in your install folders that have the same names as files in the new release will be overwritten. If you have customized any of the default files -- such as receipt templates, report templates, or the built-in Headquarters logo files -- you should back up your files and save them to another location. After the upgrade is complete, you can then copy your customized files back into the install folders and resume using them.


1.2	Upgrading to Windows Vista

Microsoft SQL Server 2000 is not supported on Windows Vista. For this reason, you must upgrade SQL Server 2000, including MSDE 2000, to SQL Server 2005 *before* you upgrade your operating system to Windows Vista. For more information, see the article "SQL Server 2000 (including MSDE 2000) on Windows Vista FAQ," located at http://www.microsoft.com/sql/prodinfo/previousversions/faq-sql_on_vista.mspx.

For information about special considerations for manual upgrades to SQL Server 2005, see section 3.3 below.


1.3	SQL Server Service Pack Updates

Microsoft SQL Server 2005 Express Edition (SQL Server Express) with Service Pack 1 (SP1) is included with Microsoft Dynamics RMS. If you prefer, you can use an existing instance of SQL Server. Be sure to download and install the latest service pack for your edition of SQL Server. For more information, see these Microsoft Web sites: www.microsoft.com/sql and http://support.microsoft.com.

Note: There are special considerations if you upgraded a named instance of SQL Server 2000 Desktop Edition (MSDE 2000) to SQL Server Express. For more information, see section 3.3 below.


1.4	Installation Model

Install Headquarters and Headquarters Server on one or more computers at the head office. Microsoft recommends running Headquarters Server on a dedicated computer (a computer not used for daily operations) if at all possible.

Install Headquarters Client at each of your stores. Activation is required.


1.5	Installing Headquarters Client

   To install Headquarters Client
      1. Install Headquarters Client from this CD.  
      2. Use the Configuration command on the File menu in Headquarters Client to (1) define the database server name and access password that Headquarters Client will use to connect to your local Store Operations database, and (2) define the database server name and access password that Headquarters Client will use to connect to Headquarters Server. 


---------------------------------------------------------------

2.	SETUP NOTES	


2.1 	Defining Network Protocols

For successful Headquarters communication, all machines must be using the same network protocols. The Microsoft Dynamics RMS installation program enables the TCP/IP and Named Pipes protocols by default. If your database server computer is using a protocol other than TCP/IP or Named Pipes, you will need to enable the protocols you want to use. To enable new protocols on any computer where Headquarters is installed, use Client Network Utility (on the Start menu, point to Microsoft Dynamics RMS, and then click Client Network Utility). For more information, click Help in the utility.

To enable new protocols on the database computer if Microsoft Dynamics RMS is not installed there, use SQL Server Configuration Manager for SQL Server 2005 or Client Network Utility for SQL Server 2000. For more information, see "Configuring Client Network Protocols" in SQL Server 2005 Books Online.


2.2	Defining Database Server Information

In Headquarters Administrator, use the Configuration command on the File menu to define the database server name and access password that Headquarters Manager will use to connect to your database server. 

Refer to the Headquarters Getting Started Guide or Headquarters Administrator Online Help for information on how to set up and use the Headquarters database.


---------------------------------------------------------------

3.	TROUBLESHOOTING

3.1	Modifying an Installation

On very rare occasions, Windows Installer may prompt for the original installation media when removing or modifying an installation of Microsoft Dynamics RMS. This is caused by the Windows Installer needing to re-cache the product's installer package. If this occurs, locate and insert the CD containing the release you are trying to remove or modify, and then follow the on-screen instructions.


3.2	Connecting to the Database Server

If you have problems connecting to SQL Server on another machine on the network, make sure that you are using the same network library on both the server and client machines. For more information, see section 2.1 above.


3.3	Creating Databases after Upgrading to SQL Server Express

If you encounter errors when creating new databases, they might be caused by a known issue with the manual upgrade from MSDE 2000 to SQL Server Express. This issue only applies to you if all of these statements are true:
	* You upgraded MSDE to the original (non-Service Pack) release of SQL Server Express.
	* You selected SQL Authentication during the upgrade to SQL Server Express.
	* You chose to skip the SQL Server installation during installation of Microsoft Dynamics RMS.
	* You are using a named instance.

In order to create Microsoft Dynamics RMS databases, you will need to uninstall and then reinstall Microsoft Dynamics RMS. In the Installation Wizard, do NOT skip SQL Server installation. Instead, allow the wizard to set up an instance of SQL Server Express that will be used by Microsoft Dynamics RMS.

Notes:
When the upgrade is handled by the Microsoft Dynamics RMS Installation Wizard, a named instance is left alone and a new unnamed default instance of SQL Server Express is created for use by Microsoft Dynamics RMS. An unnamed instance is upgraded to SQL Server Express.

By default, the instance of SQL Server Express that is installed with Microsoft Dynamics RMS will run in Compatibility Mode Level 80. Microsoft does not recommend changing this setting.


3.4	Microsoft Product Support Services

You can find technical support for Microsoft Dynamics RMS at the product support Web site, http://www.microsoft.com/dynamics/support/default.mspx.
